Skip to content

CCM-18290: Update CSV Report to use Dispatched#368

Open
gareth-allan wants to merge 5 commits into
mainfrom
feature/CCM-18290_use_dispatched_in_report
Open

CCM-18290: Update CSV Report to use Dispatched#368
gareth-allan wants to merge 5 commits into
mainfrom
feature/CCM-18290_use_dispatched_in_report

Conversation

@gareth-allan
Copy link
Copy Markdown
Contributor

@gareth-allan gareth-allan commented May 21, 2026

Description

Changes the CSV report and component tests to use DISPATCHED instead of DELIVERED. Reverts #324.

Also includes updates to package-lock.json files to update dependencies in order to resolve vulnerabilities. I've also included an update to the workspace settings for the VSCode Jest plugin, so it doesn't automatically run all unit tests when you open the project/change branch.

Context

Unfortunately we initially used Dispatched, then changed to Delivered, but we should be using Dispatched (we were referencing an out of date diagram). So we need to revert back to how things were configured.

Validation

Report Generation

Sent PrintLetterTransitioned events to this PR's event bus with both a status of DELIVERED and DISPATCHED:
Screenshot 2026-05-22 at 11 14 03
Screenshot 2026-05-22 at 13 31 07

Ran the MSCK TABLE REPAIR command against the Glue table to ensure the latest data was visible:
Screenshot 2026-05-22 at 11 42 01

Then sent a GenerateReport event to this PR's event bus, to generate a report for today:
Screenshot 2026-05-22 at 11 43 27

Verified that a report was produced:
Screenshot 2026-05-22 at 11 46 32

Dependency Updates

Output of npm audit on main:
Screenshot 2026-05-22 at 10 26 35

Output of npm audit with these changes:
Screenshot 2026-05-22 at 10 21 02

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@gareth-allan gareth-allan requested review from a team as code owners May 21, 2026 10:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants